Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update all minor dependencies (minor) #5479

Closed
wants to merge 1 commit into from
Closed

chore(deps): update all minor dependencies (minor) #5479

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@types/node (source) 20.14.14 -> 20.16.1 age adoption passing confidence devDependencies minor
@unocss/reset ^0.59.0 -> ^0.62.0 age adoption passing confidence devDependencies minor
@vite-pwa/vitepress ^0.4.0 -> ^0.5.0 age adoption passing confidence devDependencies minor
cspell (source) 8.13.1 -> 8.14.2 age adoption passing confidence devDependencies minor
cypress/included 13.7.3 -> 13.13.3 age adoption passing confidence minor
esbuild ^0.21.5 -> ^0.23.0 age adoption passing confidence devDependencies minor
font-awesome (source) 6.5.2 -> 6.6.0 age adoption passing confidence minor
langium (source) 3.0.0 -> 3.1.3 age adoption passing confidence dependencies minor
langium-cli (source) 3.0.3 -> 3.1.1 age adoption passing confidence devDependencies minor
lycheeverse/lychee-action v1.9.3 -> v1.10.0 age adoption passing confidence action minor
node (source) 20.12.2 -> 20.17.0 age adoption passing confidence minor
node 20.12.2-alpine3.19 -> 20.17.0-alpine3.19 age adoption passing confidence final minor
pnpm (source) 9.7.1+sha512.faf344af2d6ca65c4c5c8c2224ea77a81a5e8859cbc4e06b1511ddce2f0151512431dd19e6aff31f2c6a8f5f2aced9bd2273e1fed7dd4de1868984059d2c4247 -> 9.8.0 age adoption passing confidence packageManager minor
tsx (source) 4.16.5 -> 4.17.0 age adoption passing confidence devDependencies minor
type-fest 4.23.0 -> 4.25.0 age adoption passing confidence devDependencies minor
typedoc (source) ^0.25.12 -> ^0.26.0 age adoption passing confidence devDependencies minor
typescript (source) ~5.4.3 -> ~5.5.0 age adoption passing confidence devDependencies minor
typescript (source) ~5.4.5 -> ~5.5.0 age adoption passing confidence devDependencies minor
unocss ^0.59.0 -> ^0.62.0 age adoption passing confidence devDependencies minor
unplugin-vue-components ^0.26.0 -> ^0.27.0 age adoption passing confidence devDependencies minor
vite (source) 5.3.5 -> 5.4.2 age adoption passing confidence devDependencies minor
vite-plugin-pwa ^0.19.7 -> ^0.20.0 age adoption passing confidence devDependencies minor
vitepress (source) 1.1.4 -> 1.3.3 age adoption passing confidence devDependencies minor

Release Notes

unocss/unocss (@​unocss/reset)

v0.62.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.62.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.62.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.61.9

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.61.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.61.7

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.61.6

Compare Source

   🚀 Features
  • preset-mini: Support (float  -  by **end) (#​3997)** and Anthony Fu (clear)-(start)
   🐞 Bug Fixes
    View changes on GitHub

v0.61.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.61.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.61.3

Compare Source

   🚀 Features
    View changes on GitHub

v0.61.2

Compare Source

No significant changes

    View changes on GitHub

v0.61.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.60.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.60.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
  • preset-mini: Improve performance of resolveBreakpoints  -  by @​antfu (05d90)
    View changes on GitHub

v0.60.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.60.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.60.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vite-pwa/vitepress (@​vite-pwa/vitepress)

v0.5.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub
streetsidesoftware/cspell (cspell)

v8.14.2

Compare Source

v8.14.1

Compare Source

v8.13.3

Compare Source

v8.13.2

Compare Source

evanw/esbuild (esbuild)

v0.23.1

Compare Source

  • Allow using the node: import prefix with es* targets (#​3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open

// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;

// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#​3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#​3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#​3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#​3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

v0.23.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#​3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#​3818)

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

    // Original code
<Foo>
  <Bar />
</Foo>

// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;

// New output (with --jsx=preserve)
<Foo>
  <Bar />
</Foo>;

v0.22.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

  • Omit packages from bundles by default when targeting node (#​1874, #​2830, #​2846, #​2915, #​3145, #​3294, #​3323, #​3582, #​3809, #​3815)

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).

  • Drop support for older platforms (#​3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008
    • Windows Server 2012

    This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version

    In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

  • Update await using behavior to match TypeScript

    TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

  • Allow es2024 as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

  • Publish binaries for OpenBSD on 64-bit ARM (#​3665, #​3674)

    With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

    This was contributed by @​ikmckenz.

  • Publish binaries for WASI (WebAssembly System Interface) preview 1 (#​3300, #​3779)

    The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

    Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.

    This release publishes esbuild precompiled for WASI preview 1 to the @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be of

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Apr 22, 2024 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Scope: all 8 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
packages/mermaid                         |  WARN  deprecated @types/prettier@3.0.0
Progress: resolved 59, reused 52, downloaded 0, added 0
Progress: resolved 128, reused 116, downloaded 1, added 0
Progress: resolved 128, reused 116, downloaded 3, added 0
Progress: resolved 130, reused 116, downloaded 8, added 0
Progress: resolved 191, reused 161, downloaded 12, added 0
Progress: resolved 215, reused 172, downloaded 12, added 0
Progress: resolved 355, reused 308, downloaded 12, added 0
Progress: resolved 477, reused 422, downloaded 12, added 0
Progress: resolved 639, reused 596, downloaded 12, added 0
Progress: resolved 657, reused 614, downloaded 14, added 0
Progress: resolved 892, reused 856, downloaded 14, added 0
Progress: resolved 1034, reused 1000, downloaded 16, added 0
Progress: resolved 1154, reused 1114, downloaded 19, added 0
Progress: resolved 1262, reused 1198, downloaded 26, added 0
Progress: resolved 1361, reused 1260, downloaded 36, added 0
Progress: resolved 1454, reused 1343, downloaded 45, added 0
Progress: resolved 1486, reused 1363, downloaded 57, added 0
Progress: resolved 1538, reused 1408, downloaded 62, added 0
Progress: resolved 1622, reused 1493, downloaded 63, added 0
Progress: resolved 1640, reused 1511, downloaded 66, added 0
Progress: resolved 1670, reused 1539, downloaded 67, added 0
Progress: resolved 1731, reused 1594, downloaded 74, added 0
Progress: resolved 1794, reused 1654, downloaded 79, added 0
Progress: resolved 1834, reused 1693, downloaded 81, added 0
Progress: resolved 1906, reused 1766, downloaded 81, added 0
Progress: resolved 1966, reused 1824, downloaded 81, added 0
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: cytoscape@3.28.1

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

@netlify Netlify
Copy link

netlify bot commented Apr 22, 2024 •
edited
Loading

✅ Deploy Preview for mermaid-js ready!

Name Link
🔨 Latest commit a392e20
🔍 Latest deploy log https://app.netlify.com/sites/mermaid-js/deploys/66c9b1fdb2d28a000846de85
😎 Deploy Preview https://deploy-preview-5479--mermaid-js.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@codecov Codecov
Copy link

codecov bot commented Apr 22, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 5.72%. Comparing base (cf20ccb) to head (d0e5599).

❗ Current head d0e5599 differs from pull request most recent head 7b26028

Please upload reports for the commit 7b26028 to get more accurate results.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           develop   #5479      +/-   ##
==========================================
- Coverage     5.73%   5.72%   -0.01%     
==========================================
  Files          278     278              
  Lines        41999   42013      +14     
  Branches       490     490              
==========================================
- Hits          2409    2407       -2     
- Misses       39590   39606      +16
Flag Coverage Δ
unit 5.72% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 19 files with indirect coverage changes

@renovate renovate bot force-pushed the renovate/all-minor branch 6 times, most recently from d0e5599 to 92330db Compare April 30, 2024 14:09
@renovate renovate bot force-pushed the renovate/all-minor branch 10 times, most recently from f8eaaf7 to e0bfece Compare May 8, 2024 06:37
@renovate renovate bot force-pushed the renovate/all-minor branch 6 times, most recently from 8b693ba to 682ee6e Compare May 13, 2024 06:44
@renovate renovate bot force-pushed the renovate/all-minor branch 5 times, most recently from 3def21a to 95ad0ed Compare May 21, 2024 10:25
@renovate renovate bot force-pushed the renovate/all-minor branch 7 times, most recently from aff0367 to 1c99982 Compare August 6, 2024 16:41
@renovate renovate bot force-pushed the renovate/all-minor branch 13 times, most recently from 039a1b5 to b50c13f Compare August 12, 2024 12:41
@renovate renovate bot changed the title chore(deps): update all minor dependencies (minor) Update all minor dependencies (minor) Aug 12, 2024
@renovate renovate bot force-pushed the renovate/all-minor branch 2 times, most recently from 68d51f3 to f812e15 Compare August 13, 2024 16:26
@renovate renovate bot changed the title Update all minor dependencies (minor) chore(deps): update all minor dependencies (minor) Aug 13, 2024
@renovate renovate bot force-pushed the renovate/all-minor branch 2 times, most recently from 3ee14ad to d2e1587 Compare August 15, 2024 15:45
@renovate renovate bot force-pushed the renovate/all-minor branch from cab8764 to a392e20 Compare August 24, 2024 10:12
@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Aug 24, 2024

⚠️ No Changeset found

Latest commit: a392e20

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@codecov-commenter @sidharthv96